Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle release already existing when uploading release notes #83

Merged
merged 1 commit into from
Jan 28, 2025

Conversation

SeanTAllen
Copy link
Member

Previously, the uploading of release notes assumed that the release didn't exist yet. This made sense for all our ponylang usage. However, for other projects that create assets as part of the build process and store them in GitHub releases rather than Cloudsmith, the release might already exist.

Now, we will check to see if the release exists. If it does, we update it with our release notes. If it doesn't, we will create the release like we previously did.

@SeanTAllen SeanTAllen added the changelog - fixed Automatically add "Fixed" CHANGELOG entry on merge label Jan 28, 2025
@ponylang-main ponylang-main added the discuss during sync Should be discussed during an upcoming sync label Jan 28, 2025
@ponylang-main
Copy link
Contributor

Hi @SeanTAllen,

The changelog - fixed label was added to this pull request; all PRs with a changelog label need to have release notes included as part of the PR. If you haven't added release notes already, please do.

Release notes are added by creating a uniquely named file in the .release-notes directory. We suggest you call the file 83.md to match the number of this pull request.

The basic format of the release notes (using markdown) should be:

## Title

End user description of changes, why it's important,
problems it solves etc.

If a breaking change, make sure to include 1 or more
examples what code would look like prior to this change
and how to update it to work after this change.

Thanks.

Previously, the uploading of release notes assumed that the release
didn't exist yet. This made sense for all our ponylang usage. However,
for other projects that create assets as part of the build process
and store them in GitHub releases rather than Cloudsmith, the release
might already exist.

Now, we will check to see if the release exists. If it does, we update
it with our release notes. If it doesn't, we will create the release
like we previously did.
@SeanTAllen SeanTAllen force-pushed the upload-release-notes-when-release-exists branch from aa8a9ce to a713b29 Compare January 28, 2025 21:22
@SeanTAllen SeanTAllen merged commit 0cd85b6 into main Jan 28, 2025
10 checks passed
@SeanTAllen SeanTAllen deleted the upload-release-notes-when-release-exists branch January 28, 2025 21:24
@ponylang-main ponylang-main removed the discuss during sync Should be discussed during an upcoming sync label Jan 28, 2025
github-actions bot pushed a commit that referenced this pull request Jan 28, 2025
github-actions bot pushed a commit that referenced this pull request Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog - fixed Automatically add "Fixed" CHANGELOG entry on merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants